Mechanism to enhance user experience of mobile devices through complex inputs from external displays

ABSTRACT

A method of mapping user movements captured by a capture device external to a computing device, to inputs events on the computing device, may comprise executing an application on the computing device, using at least one processor of the computing device. The computing device may transmit video data of the application to a receiver device. The computing device may receive gesture data associated with the application, the gesture data based on movements of a user captured from a capture device communicatively coupled to the receiver device. The gesture data may be mapped to an input event on the computing device and data simulating the input event may be provided to a sensor on the computing device.

TECHNICAL FIELD

Embodiments described herein generally relate to input processing and inparticular, but not limited to, a mechanism to enhance user experienceof mobile devices through complex inputs from external displays.

BACKGROUND

Mobile devices such as phones and tablets may include the ability toconnect to external displays. For example, a mobile phone may have aHigh-Definition Multimedia Interface (HDMI) port to connect to atelevision or the phone may be able to wirelessly stream video to thetelevision. In some cases, the mobile device may mirror what is beingshown on the mobile device to the external display.

BRIEF DESCRIPTION OF THE DRAWINGS

In the drawings, which are not necessarily drawn to scale, like numeralsmay describe similar components in different views. Like numerals havingdifferent letter suffixes may represent different instances of similarcomponents. Some embodiments are illustrated by way of example, and notlimitation, in the figures of the accompanying drawings in which:

FIG. 1 is an illustration of a user interacting with an externaldisplay, according to an embodiment;

FIG. 2 is a block diagram illustrating a computing device, according toan embodiment;

FIG. 3 is a block diagram illustrating a capturing system, according toan embodiment;

FIG. 4 is a flow chart illustrating a method of mapping inputs from areceiver device to a computing device, according to an embodiment;

FIG. 5 is a block diagram illustrating a capturing system, according toan embodiment; and

FIG. 6 is a block diagram illustrating an example machine upon which anyone or more of the techniques (e.g., methodologies) discussed herein mayperform, according to an example embodiment.

DETAILED DESCRIPTION

Many mobile devices, such as a smart phone, have the ability to streamcontent from the mobile device to an external display. For example, auser may take a video with the user's mobile phone and then display thevideo on the user's television set. To accomplish this, the user mayestablish a connection (e.g., via a wireless or wired connection)between the mobile phone and the television and click or otherwiseactivate a function on the mobile phone to begin streaming the videofrom the mobile phone to the television. In some instances everythingthat is displayed on the mobile phone is mirrored (e.g., displayed) onthe television.

In various examples, a user may open an application that is installed onthe mobile phone and have the application displayed on the television.The application may be a game in which the sensors of the mobile phoneare used to control the game, but the user may view his or her progressof the game on the television. For example, consider that theapplication is a racing game and that a gyroscope sensor in the mobilephone senses when the user tilts the mobile phone left or right. Theracing game then updates the objects (e.g., the car) and displays thechange on the mobile phone and, because the mobile phone has aconnection to the television, the change will be mirrored on thetelevision.

In an example, the television may be connected to additional inputdevices that are more complex than sensors installed on the mobilephone. For example, a camera may be placed near or in the televisionthat captures user movement and determines a gesture that the user hasmade. However, despite the availability of these more complex inputs,any captured inputs made using such devices may not be available to themobile phone or its running applications.

Accordingly, many application developers do not write applications thattake advantage of these complex inputs and instead rely on the sensorsand inputs of the mobile phone. In various examples described herein,various mechanisms are described that allows for complex inputs to bemapped back to the sensors of the mobile phone. In various examples, anapplication developer does not need to change an application to takeadvantage of these complex inputs.

FIG. 1 is an illustration 100 of a user 102 interacting with an externaldisplay 106, according to an embodiment. The illustration 100 furtherdepicts a computing device 104 and a capture device 108. As illustrated,the display of computing device 104 is showing an image that is thatsame as that displayed on external display 106. Additionally, the user102 is making a jumping motion which is partially reflected by thesnowboarding character being displayed on the computing device 104 andthe external display 106.

FIG. 2 is a block diagram illustrating a computing device 200, accordingto an embodiment. The computing device may include a client sharingmodule 202, a mapping module 204, a gyroscope sensor 206, anaccelerometer sensor 208, a touch sensor 210, an application 212, videodata 214, gesture data 216, a video channel 218, and an input channel220.

In various examples, the computing device 200 is a portable deviceincluding, but not limited to, a smart phone, tablet, or laptopcomputer. In an example the computing device 104 includes atouch-enabled display. The computing device 104 may include at least oneprocessor that executes operating system software stored on anon-transitory computer-readable medium (e.g., flash storage, RAM, harddrive etc.). The application 212 may also be stored on the same ordifferent non-transitory computer-readable medium. The computing device104 may have other applications as well that are not illustrated.

In various examples, the computing device 200 establishes one or moreconnections with a receiver device (e.g., a receiver device 302illustrated and discussed further herein with respect to FIG. 3). Theone or more connections may be used to transfer video data and inputdata between the computing device 200 and the receiver device. Invarious example, the connections are wired or wireless (e.g., HDMI,Wi-Fi, Wi-Fi Direct, Bluetooth, NFC, Ethernet). Different types of datamay also be transferred between the computing device 200 and thereceiver device 302 over the connections. Additionally, the data may becarried over the connections using different communication protocols.

In various example, the computing device 200 and receiver device 302communicate via a network. The network may include local-area networks(LAN), wide-area networks (WAN), wireless networks (e.g., 802.11 orcellular network), the Public Switched Telephone Network (PSTN) network,ad hoc networks, personal area networks or peer-to-peer (e.g.,Bluetooth®, Wi-Fi Direct), or other combinations or permutations ofnetwork protocols and network types. The network may include a singlelocal area network (LAN) or wide-area network (WAN), or combinations ofLAN's or WAN's, such as the Internet

In various examples, a user may direct the computing device 200 toestablish one of the above described connections with a compatiblereceiver device. For example, a user may launch the application 212 andthe application 212 may present an option to share or mirror video ofthe application with an external device. The option may include a listof compatible (e.g., able to receive streaming video) devices withinrange of the computing device such as TVs. A user may select one of theavailable devices and then the computing device 302 may transmit arequest to the selected device to initiate video streaming to theselected device. The application 212 may be a gaming application, videoplayback application, music playback application, according to variousexample embodiments.

FIG. 2 illustrates two data channels, the video channel 218 and theinput channel 220 which may be transmitted over one or more of theconnections described previously. Thus, in various examples, the videodata 214 may be transmitted on a separate data channel than the gesturedata 216, however, in other embodiments a shared data channel may beutilized. The data channels may use different protocols to transmit thevideo data 214 and gesture data 216.

For example, the video data 214 may be transmitted to a receiver deviceusing the real-time transport protocol (RTP) over the video channel 218,whereas the gesture data 216 may be received by the computing device 214using a user input back channel (UIBC) or consumer electronics control(CEC) over the input channel 220. In various examples, client sharingmodule 202 handles the transmission of the video data 214 and receptionof the gesture data 216.

In various examples, the video data 214 is a video stream of theapplication 212 currently being executed and displayed on a display ofthe computing device 200. In an example, the video data 214 is notdisplayed on the computing device 200 but it still associated with anapplication executing on the computing device 200 (e.g., the display ofthe computing device is off because to user is using a TV for thedisplay of the application). The video data 214 may be compressed by theclient sharing module 202 before being transmitted. For example, variousWi-Fi based screen sharing frameworks (e.g., Intel WiDi®, AppleAirplay®, Miracast) compress the video using one or more codecs (e.g.,H.264) because the wireless connection may not be able to support thefull bitrate of the video.

In various examples, the gesture data 216 is data identifying one ormore movements made by the user. The gesture data 216 may include a typeof movement and characteristics of the movement. Types of movement mayinclude, but are not limited to leaning movements, swiping movements,and shaking movements. Different types of movements may have differentcharacteristics. For example, a lean movement may include a directioncharacteristic (e.g., forward, backward, left, right) and degreecharacteristic (e.g., 30 degrees) whereas a swiping movement may onlyhave a direction characteristic.

In various examples, the mapping module 204 maps the gesture data 216into an input event and provides data simulating the input event to asensor of the computing device 200. The table below is an examplemapping of gesture data to sensors:

Translated Input Sensor to simulate User Gesture Event input eventLeaning to the Rotation events of 0 Gyroscope left/right to −/+90degrees (left/right rotation) Swiping motion to Multiple touch eventsTouch the left/right ranging from middle of the screen towards the mid-left/mid-right end of the screen Shaking motion/ Acceleration eventsAccelerometer Gestures (e.g., movement of the device) how fast thedevice was moved) Pick-up gesture Placing a hand or Proximity Sensorobject near the face of the mobile deviceThe above table provides various examples, and others mappings and usergestures may be used. The mappings between gestures, input events, andsensors may be stored on the computing device 200 and accessed by themapping module 204 when processing the gesture data 216.

The data received by the sensor may be based on the mapping andcharacteristics of the gesture data 216. For example, consider a userwho make a leaning gesture to the left approximately half-way toparallel to the floor. The gesture data 216 may identify the gesture asa lean movement with a direction characteristic of left and a degreecharacteristic of 45. Then, the mapping module 214 may translate themovement into a rotate input event to the left of 45 degrees. Finally,the mapping module 214 may provide data to the gyroscope consistent witha user rotating the computing device 45 degrees to the left therebysimulating the input event. In various examples, gesture data thattranslates to a touch event include coordinate data representing thetouch points on the screen. In an example, the sensor may be a “dumb”sensor that outputs raw data based on movements of the phone and thusproviding data directly to the sensor may not be practical. In suchcases the simulated data may be provided to a driver of the sensor, andtherefore the input event may still be simulated with no change to theapplication 212.

In various examples, the application 212 updates based on the dataprovided to the sensors. In other words, even though the computingdevice 200 was not actually moved or touched, the sensors of thecomputing device 200 provide data to the application 212 as if this wastrue, and the application 212 updates accordingly.

In addition to motion gestures, voice data received via the receiverdevice may also be transmitted to the computing device 200 via the inputchannel 220. The voice data may be mapped to one or more sensors. Forexample, voice recognition may be run on the voice data and theresulting word(s) matched to a gesture event such as having the word“back” mapped to a swipe left. Then, the gesture may be mapped to asensor as described above.

FIG. 3 is a block diagram illustrating a capturing system 300, accordingto an embodiment. Capturing system 300 may include the receiver device302, the receiver sharing module 304, the input capturing module 306,the display 308, the camera 310, movement data 312, and red, green, blue(RGB) and depth data 312. While the receiver device 302, display 308,and camera 310 are illustrated as separate components, these devices mayall be part of a shared system (e.g., a television with a built-incamera). In various examples, the receiver device 302 and the camera 310are communicatively coupled to the display 308 (e.g., via a USBconnection).

In various examples, the receiver sharing module 304 is the companion tothe client sharing module 202 and have a common sharing framework. In anexample, the client sharing module 202 may be considered the “source”and the receiver sharing module 304 the “sink.” In various examples, thereceiver sharing module 304 receives the video data 214 over the videochannel 218 and the gesture data 216 is transmitted to the computingdevice 200 via the input channel 220. Additionally, the receiver sharingmodule 304 transmit the video data 214 to the display 308, which in turndisplays the video data. In some examples, the receiver sharing module304 decompresses the video data 214 before transmitting it to thedisplay 308.

In an example, the receiver sharing module 304 receives the gesture data216 from the input capturing module 306. To generate the gesture data216, the input capturing module 306 may process the RGB and depth data312 captured by the camera 310. In an example, a user makesmovements/gestures to interact with objects displayed in the video data218 of the application 212. These gestures/movements may be captured asa series of frames that each include color information (e.g., RGB data)and depth information (e.g., how far away from the camera 310 each pointin the frame is), collectively user movement data.

In an example, various gesture detecting frameworks may be utilized bythe input capturing module 306 to analyze the RGB and depth data 312.For example, the analysis may track objects (e.g., a hand) present inthe RGB and depth data 312 over a series of frames and match themovement to a profile of user gestures. The results of the analysis maybe a user gesture type and characterizations of the gesture that ispackaged as the gesture data 216.

FIG. 4 is a flow chart illustrating a method of mapping inputs from areceiver device to a computing device, according to an embodiment. In anexample, at operation 402, an application is executed on a computingdevice, using at least one processor of the computing device. Forexample, a user may select an icon, representing a gaming application,on the touch screen of a smart phone to open the application.

In an example, at operation 404, video data from the computing device istransmitted to a receiver device. The receiver device may be a devicecommunicatively coupled to a display or be part of the display itself.In an example, one or more data channels are established between thereceiver device and the computing device. For example, a video channel(e.g., over an HDMI cable or WiDi) may be established and the video datatransmitted over the video channel. In various examples, video displayedon a display of the computing device is streamed to the receiver deviceover the video channel.

In an example, at operation 406, gesture data is received at thecomputing device from the receiver device. In an example, the gesturedata is received over an input channel established between the receiverdevice and the computing device. The input channel may be establishedseparately than the video channel.

The gesture data may be associated with the application captured from acapture device communicatively coupled to the receiver device. In anexample, associated means that a user has made a movement or gesturerelated to objects displayed on a display communicatively coupled to thereceiver device or related to a function of the application. In anexample, the capture device is a camera. In an example, the gesture dataincludes a type of gesture (e.g., a lean) and characteristics of thegesture (e.g., speed, angle, position).

In an example, at operation 408, the gesture data may be mapped to aninput event. For example, a table or other data structures may beaccessed that include a mapping of types of gestures to input eventsassociated with the computing device. For example, a lean gesture typemay be stored as associated with a rotate input event consistent withrotating the computing device. In an example, at operation 410, datasimulating the input event is provided to a sensor on the computingdevice. Continuing the example of a lean event, data simulating rotatingthe computing device may be provided to a gyroscope of the computingdevice. In an example, where the input event is a touch input event,data simulating a touch event may be provided to a touch sensor (e.g.,the touch display) of the computing device. In an example, the videodata may be updated based on the application responding to sensorsreceiving the simulated events. The updated video data may betransmitted to the receiver device.

FIG. 5 is a block diagram illustrating a capturing system 500, accordingto an embodiment. Capturing system 500 may be similar to capturingsystem 300 except that capturing system 500 includes a mapping module502 and mapped input 504. Thus, in various examples instead of, or inaddition to, a mobile computing device having a mapping module, thecapturing system 500 may include the mapping module 502. In suchinstances, the gesture data 216 may be passed first to the mappingmodule 502.

Similarly to the mapping module 204, the mapping module 502 may map thegesture data 216 to an input event and generate data simulating theevent. The generated data may be transmitted to the computing device 200as the mapped input 504 via receiver sharing module 304 and the inputchannel 220. The computing device 200 may then take the mapped input 504and pass the data directly to a sensor of the computing device 200 or adriver of a sensor the computing device 200. In an example, the mappedinput 504 include an indication of which sensor to provide the data toon the computing device.

Example Computer System

Embodiments may be implemented in one or a combination of hardware,firmware, and software. Embodiments may also be implemented asinstructions stored on a machine-readable storage device, which may beread and executed by at least one processor to perform the operationsdescribed herein. A machine-readable storage device may include anynon-transitory mechanism for storing information in a form readable by amachine (e.g., a computer). For example, a machine-readable storagedevice may include read-only memory (ROM), random-access memory (RAM),magnetic disk storage media, optical storage media, flash-memorydevices, and other storage devices and media.

Examples, as described herein, may include, or may operate on, logic ora number of components, modules, or mechanisms. Modules may be hardware,software, or firmware communicatively coupled to one or more processorsin order to carry out the operations described herein. Modules mayhardware modules, and as such modules may be considered tangibleentities capable of performing specified operations and may beconfigured or arranged in a certain manner. In an example, circuits maybe arranged (e.g., internally or with respect to external entities suchas other circuits) in a specified manner as a module. In an example, thewhole or part of one or more computer systems (e.g., a standalone,client or server computer system) or one or more hardware processors maybe configured by firmware or software (e.g., instructions, anapplication portion, or an application) as a module that operates toperform specified operations. In an example, the software may reside ona machine-readable medium. In an example, the software, when executed bythe underlying hardware of the module, causes the hardware to performthe specified operations. Accordingly, the term hardware module isunderstood to encompass a tangible entity, be that an entity that isphysically constructed, specifically configured (e.g., hardwired), ortemporarily (e.g., transitorily) configured (e.g., programmed) tooperate in a specified manner or to perform part or all of any operationdescribed herein. Considering examples in which modules are temporarilyconfigured, each of the modules need not be instantiated at any onemoment in time. For example, where the modules comprise ageneral-purpose hardware processor configured using software; thegeneral-purpose hardware processor may be configured as respectivedifferent modules at different times. Software may accordingly configurea hardware processor, for example, to constitute a particular module atone instance of time and to constitute a different module at a differentinstance of time. Modules may also be software or firmware modules,which operate to perform the methodologies described herein.

FIG. 6 is a block diagram illustrating a machine in the example form ofa computer system 600, within which a set or sequence of instructionsmay be executed to cause the machine to perform any one of themethodologies discussed herein, according to an example embodiment. Inalternative embodiments, the machine operates as a standalone device ormay be connected (e.g., networked) to other machines. In a networkeddeployment, the machine may operate in the capacity of either a serveror a client machine in server-client network environments, or it may actas a peer machine in peer-to-peer (or distributed) network environments.The machine may be a personal computer (PC), a tablet PC, a hybridtablet, a set-top box (STB), a personal digital assistant (PDA), amobile telephone, a web appliance, a network router, switch or bridge,or any machine capable of executing instructions (sequential orotherwise) that specify actions to be taken by that machine. Further,while only a single machine is illustrated, the term “machine” shallalso be taken to include any collection of machines that individually orjointly execute a set (or multiple sets) of instructions to perform anyone or more of the methodologies discussed herein.

Example computer system 600 includes at least one processor 602 (e.g., acentral processing unit (CPU), a graphics processing unit (GPU) or both,processor cores, compute nodes, etc.), a main memory 604 and a staticmemory 606, which communicate with each other via a link 608 (e.g.,bus). The computer system 600 may further include a video display unit610, an alphanumeric input device 612 (e.g., a keyboard), and a userinterface (UI) navigation device 614 (e.g., a mouse). In one embodiment,the video display unit 610, input device 612 and UI navigation device614 are incorporated into a touch screen display. The computer system600 may additionally include a storage device 616 (e.g., a drive unit),a signal generation device 618 (e.g., a speaker), a network interfacedevice 620, and one or more sensors (not shown), such as a globalpositioning system (GPS) sensor, compass, accelerometer, or othersensor.

The storage device 616 includes a machine-readable medium 622 on whichis stored one or more sets of data structures and instructions 624(e.g., software) embodying or utilized by any one or more of themethodologies or functions described herein. The instructions 624 mayalso reside, completely or at least partially, within the main memory604, static memory 606, and/or within the processor 602 during executionthereof by the computer system 600, with the main memory 604, staticmemory 606, and the processor 602 also constituting machine-readablemedia.

While the machine-readable medium 622 is illustrated in an exampleembodiment to be a single medium, the term “machine-readable medium” mayinclude a single medium or multiple media (e.g., a centralized ordistributed database, and/or associated caches and servers) that storethe one or more instructions 624. The term “machine-readable medium”shall also be taken to include any tangible medium that is capable ofstoring, encoding or carrying instructions for execution by the machineand that cause the machine to perform any one or more of themethodologies of the present disclosure or that is capable of storing,encoding or carrying data structures utilized by or associated with suchinstructions. The term “machine-readable medium” shall accordingly betaken to include, but not be limited to, solid-state memories, andoptical and magnetic media. Specific examples of machine-readable mediainclude non-volatile memory, including, but not limited to, by way ofexample, semiconductor memory devices (e.g., electrically programmableread-only memory (EPROM), electrically erasable programmable read-onlymemory (EEPROM)) and flash memory devices; magnetic disks such asinternal hard disks and removable disks; magneto-optical disks; andCD-ROM and DVD-ROM disks.

The instructions 624 may further be transmitted or received over acommunications network 626 using a transmission medium via the networkinterface device 620 utilizing any one of a number of well-knowntransfer protocols (e.g., HTTP). Examples of communication networksinclude a local area network (LAN), a wide area network (WAN), theInternet, mobile telephone networks, plain old telephone (POTS)networks, and wireless data networks (e.g., Wi-Fi, 3G, and 4G LTE/LTE-Aor WiMAX networks). The term “transmission medium” shall be taken toinclude any intangible medium that is capable of storing, encoding, orcarrying instructions for execution by the machine, and includes digitalor analog communications signals or other intangible medium tofacilitate communication of such software.

Example 1 includes subject matter (such as a device, apparatus, ormachine) comprising a computing device for mapping user movementscaptured by a capture device external to a computing device, to inputsevents on the computing device, the computing device comprising: adisplay to display an application executing on the computing device; aclient sharing module to: transmit video data of the application to areceiver device; and receive gesture data associated with theapplication, the gesture data based on movements of a user captured froma capture device communicatively coupled to the receiver device; and amapping module to: map the gesture data into an input event on thecomputing device; and provide data simulating the input event to asensor of the computing device.

In Example 2, the subject matter of Example 1 may include, wherein tomap the gesture data into an input event on the computing device, themapping module is to: retrieve a type of movement of the user from thegesture data; and determine the input event based on the type ofmovement.

In Example 3, the subject matter of any one or more of Examples 1 to 2may include, wherein when the type of movement of the user is a swipemovement the gesture data is mapped to a touch input event and datasimulating the touch input event is provided to a touch sensor of thecomputing device.

In Example 4, the subject matter of any one or more of Examples 1 to 3may include, wherein when the type of movement of the user is a leanmovement the gesture data is mapped to a rotate input event and datasimulating the rotate input event is provided to a gyroscope of thecomputing device.

In Example 5, the subject matter of any one or more of Examples 1 to 4may include, wherein the client sharing module is to: establish a videochannel between the computing device and receiver device; establish aninput channel between the and computing device and receiver device; andwherein the video data is transmitted over the video channel and gesturedata is received via the input channel.

In Example 6, the subject matter of any one or more of Examples 1 to 5may include, wherein to transmit video data of the application to areceiver device the sharing module is to: stream video displayed on thedisplay of the computing device to the receiver device via the videochannel.

In Example 7, the subject matter of any one or more of Examples 1 to 6may include, wherein the client sharing module is to transmit updatedvideo data to the receiver device based on the application updating inresponse to the input event.

In Example 8, the subject matter of any one or more of Examples 1 to 7may include, wherein the computing device is a mobile phone.

In Example 9, the subject matter of any one or more of Examples 1 to 8may include, wherein the receiver device is a television.

Example 10 includes or may be combined with the subject matter of anyone of Examples 1-9 to include subject matter for mapping user movementscaptured by a capture device external to a computing device, to inputsevents on the computing device (such as a method, means for performingacts, machine readable medium including instructions that when performedby a machine cause the machine to performs acts, or an apparatusconfigured to perform) comprising executing an application on acomputing device, using at least one processor of the computing device;transmitting, from the computing device, video data of the applicationto a receiver device; receiving, at the computing device from thereceiver device, gesture data associated with the application, thegesture data based on movements of a user captured from a capture devicecommunicatively coupled to the receiver device; mapping the gesture datato an input event on the computing device; and providing data simulatingthe input event to a sensor on the computing device.

In Example 11, the subject matter of Example 10 may include, whereinmapping the gesture data into an input event on the computing devicecomprises: retrieving a type of movement of the user from the gesturedata; and determining the input event based on the type of movement.

In Example 12, the subject matter of any one or more of Examples 10 to11 may include, wherein mapping the gesture data into an input eventfurther comprises: mapping the gesture data to a touch input event whenthe type of movement is a swipe movement.

In Example 13, the subject matter of any one or more of Examples 10 to12 may include, wherein providing the data simulating the input event tothe sensor on the computing device comprises: providing data simulatingthe touch input event to a touch sensor on the computing device.

In Example 14, the subject matter of any one or more of Examples 10 to13 may include, wherein mapping the gesture data into an input eventfurther comprises: mapping the gesture data to a rotate input event whenthe type of movement is a lean movement.

In Example 15, the subject matter of any one or more of Examples 10 to14 may include, wherein providing the data simulating the input event tothe sensor on the computing device comprises: providing data simulatingthe rotate input event to a gyroscope sensor on the computing device.

In Example 16, the subject matter of any one or more of Examples 10 to15 may include, establishing a video channel between the computingdevice and receiver device; establishing an input channel between thecomputing device and the receiver device; and wherein the video data istransmitted over the video channel and gesture data is received via theinput channel.

In Example 17, the subject matter of any one or more of Examples 10 to16 may include, wherein transmitting video data of the application to areceiver device comprises: streaming video displayed on a display of thecomputing device to the receiver device via the video channel.

In Example 18, the subject matter of any one or more of Examples 10 to17 may include, wherein streaming video displayed on a display of thecomputing device to the receiver device comprises: wirelessly streamingthe video to the receiver device.

In Example 19, the subject matter of any one or more of Examples 10 to18 may include, transmitting updated video data to the receiver devicebased on the application updating in response to the input event.

Example 20 includes or may optionally be combined with the subjectmatter of any one of Examples 1-19 to include an apparatus comprisingmeans for performing any of the Examples 1-19.

Example 21 includes an apparatus for mapping user movements captured bya capture device external to the computing device to inputs events onthe computing device, the apparatus comprising means for executing anapplication on the computing device; means for transmitting, from thecomputing device, video data of the application to a receiver device;means for receiving, at the computing device from the receiver device,gesture data associated with the application, the gesture data based onmovements of a user captured from a capture device communicativelycoupled to the receiver device; means for mapping the gesture data to aninput event on the computing device; and means for providing datasimulating the input event to a sensor on the computing device.

Example 22 includes subject matter (such as a device, apparatus, ormachine) comprising a capturing system to map user movements captured bya capture device to inputs events on a computing device, the systemcomprising: a receiver sharing module to receive video data of anapplication executing on a computing device external to the capturingsystem; an input capturing module to: receive user movement data of auser; and process the user movement data to determine a user gesturetype and output gesture data; a mapping module to: receive the gesturedata from the input capturing module; and map the gesture data into aninput event on the computing device; generate mapped input datasimulating the input event; and wherein the receiver sharing module isto transmit the mapped input data to the computing device.

In Example 23, the subject matter of Example 22 may include, wherein tomap the gesture data into an input event on the computing device, themapping module is to: retrieve a type of movement of the user from thegesture data; and determine the input event based on the type ofmovement.

In Example 24, the subject matter of any one or more of Examples 22 to23 may include wherein when the type of movement of the user is a swipemovement the gesture data is mapped to a touch input event and whereinthe mapped input data includes data simulating the touch input event fora touch sensor of the computing device.

In Example 25, the subject matter of any one or more of Examples 22 to24 may include wherein when the type of movement of the user is a leanmovement the gesture data is mapped to a rotate input event and whereinthe mapped input include data simulating the rotate input event isprovided for a gyroscope of the computing device.

Example 26 includes or may be combined with the subject matter of anyone of Examples 22-25 to include subject matter for mapping usermovements captured by a capture device to inputs events on a computingdevice (such as a method, means for performing acts, machine readablemedium including instructions that when performed by a machine cause themachine to performs acts, or an apparatus configured to perform)comprising receiving video data of an application executing on acomputing device external to the capturing system; receiving usermovement data of a user; processing the user movement data to determinea user gesture type and output gesture data; mapping the gesture datainto an input event for the computing device; generating mapped inputdata simulating the input event; and transmitting the mapped input datato the computing device.

In Example 27, the subject matter of Example 26 may include whereinmapping the gesture data into an input event for the computing devicecomprises: retrieving a type of movement of the user from the gesturedata; and determining the input event based on the type of movement.

In Example 28, the subject matter of any one or more of Examples 26 to27 may include wherein when the type of movement of the user is a swipemovement the gesture data is mapped to a touch input event and whereinthe mapped input data includes data simulating the touch input event fora touch sensor of the computing device.

In Example 29, the subject matter of any one or more of Examples 26 to28 may include wherein when the type of movement of the user is a leanmovement the gesture data is mapped to a rotate input event and whereinthe mapped input include data simulating the rotate input event isprovided for a gyroscope of the computing device.

Example 30 includes or may optionally be combined with the subjectmatter of any one of Examples 1-29 to include an apparatus comprisingmeans for performing any of the Examples 1-29.

Example 31 includes an apparatus for mapping user movements captured bya capture device to inputs events on a computing device, the apparatuscomprising means for receiving video data of an application executing ona computing device external to the capturing system; means for receivinguser movement data of a user; means for processing the user movementdata to determine a user gesture type and output gesture data; means formapping the gesture data into an input event for the computing device;means for generating mapped input data simulating the input event; andmeans for transmitting the mapped input data to the computing device.

The above description is intended to be illustrative, and notrestrictive. For example, the above-described examples (or one or moreaspects thereof) may be used in combination with others. Otherembodiments may be used, such as by one of ordinary skill in the artupon reviewing the above description. The Abstract is to allow thereader to quickly ascertain the nature of the technical disclosure, forexample, to comply with 37 C.F.R. §1.72(b) in the United States ofAmerica. It is submitted with the understanding that it will not be usedto interpret or limit the scope or meaning of the claims. Also, in theabove Detailed Description, various features may be grouped together tostreamline the disclosure. However, the claims may not set forth everyfeature disclosed herein as embodiments may feature a subset of saidfeatures. Further, embodiments may include fewer features than thosedisclosed in a particular example. Thus, the following claims are herebyincorporated into the Detailed Description, with a claim standing on itsown as a separate embodiment. The scope of the embodiments disclosedherein is to be determined with reference to the appended claims, alongwith the full scope of equivalents to which such claims are entitled.

What is claimed is:
 1. A computing device for mapping user movementscaptured by a capture device external to the computing device, to inputsevents on the computing device, the computing device comprising: adisplay to display an application executing on the computing device; aclient sharing module to: transmit video data of the application to areceiver device; and receive gesture data associated with theapplication, the gesture data based on movements of a user captured froma capture device communicatively coupled to the receiver device; and amapping module to: map the gesture data into an input event on thecomputing device; and provide data simulating the input event to asensor of the computing device.
 2. The computing device of claim 1,wherein to map the gesture data into an input event on the computingdevice, the mapping module is to: retrieve a type of movement of theuser from the gesture data; and determine the input event based on thetype of movement
 3. The computing device of claim 2, wherein when thetype of movement of the user is a swipe movement the gesture data ismapped to a touch input event and data simulating the touch input eventis provided to a touch sensor of the computing device.
 4. The computingdevice of claim 2, wherein when the type of movement of the user is alean movement the gesture data is mapped to a rotate input event anddata simulating the rotate input event is provided to a gyroscope of thecomputing device.
 5. The computing device of claim 1, wherein the clientsharing module is to: establish a video channel between the computingdevice and receiver device; establish an input channel between the andcomputing device and receiver device; and wherein the video data istransmitted over the video channel and gesture data is received via theinput channel.
 6. The computing device of claim 1, wherein to transmitvideo data of the application to a receiver device the sharing module isto: stream video displayed on the display of the computing device to thereceiver device via the video channel.
 7. The computing device of claim1, wherein the client sharing module is to transmit updated video datato the receiver device based on the application updating in response tothe input event.
 8. The computing device of claim 1, wherein thecomputing device is a mobile phone.
 9. The computing device of claim 1,wherein the receiver device is a television.
 10. A method of mappinguser movements captured by a capture device external to a computingdevice, to inputs events on the computing device, the method comprising:executing an application on the computing device, using at least oneprocessor of the computing device; transmitting, from the computingdevice, video data of the application to a receiver device; receiving,at the computing device from the receiver device, gesture dataassociated with the application, the gesture data based on movements ofa user captured from a capture device communicatively coupled to thereceiver device; mapping the gesture data to an input event on thecomputing device; and providing data simulating the input event to asensor on the computing device.
 11. The method of claim 10, whereinmapping the gesture data into an input event on the computing devicecomprises: retrieving a type of movement of the user from the gesturedata; and determining the input event based on the type of movement. 12.The method of claim 11, wherein mapping the gesture data into an inputevent further comprises: mapping the gesture data to a touch input eventwhen the type of movement is a swipe movement.
 13. The method of claim12, wherein providing the data simulating the input event to the sensoron the computing device comprises: providing data simulating the touchinput event to a touch sensor on the computing device.
 14. The method ofclaim 11, wherein mapping the gesture data into an input event furthercomprises: mapping the gesture data to a rotate input event when thetype of movement is a lean movement.
 15. The method of claim 14, whereinproviding the data simulating the input event to the sensor on thecomputing device comprises: providing data simulating the rotate inputevent to a gyroscope sensor on the computing device.
 16. The method ofclaim 10, further comprising: establishing a video channel between thecomputing device and receiver device; establishing an input channelbetween the computing device and the receiver device; and wherein thevideo data is transmitted over the video channel and gesture data isreceived via the input channel.
 17. The method of claim 16, whereintransmitting video data of the application to a receiver devicecomprises: streaming video displayed on a display of the computingdevice to the receiver device via the video channel.
 18. The method ofclaim 17, wherein streaming video displayed on a display of thecomputing device to the receiver device comprises: wirelessly streamingthe video to the receiver device.
 19. The method of claim 10, furthercomprising: transmitting updated video data to the receiver device basedon the application updating in response to the input event.
 20. At leastone machine-readable storage medium including instructions for mappinguser movements captured by a capture device external to a computingdevice to inputs events on the computing device, which when executed bya machine, cause the machine to perform operations comprising: executingan application on the computing device; transmitting, from the computingdevice, video data of the application to a receiver device; receiving,at the computing device from the receiver device, gesture dataassociated with the application, the gesture data based on movements ofa user captured from a capture device communicatively coupled to thereceiver device; mapping the gesture data to an input event on thecomputing device; and providing data simulating the input event to asensor on the computing device.
 21. The at least one machine-readablestorage medium of claim 20, wherein mapping the gesture data into aninput event on the computing device comprises: retrieving a type ofmovement of the user from the gesture data; and determining the inputevent based on the type of movement.
 22. A capturing system to map usermovements captured by a capture device to inputs events on a computingdevice, the system comprising: a receiver sharing module to receivevideo data of an application executing on a computing device external tothe capturing system; an input capturing module to: receive usermovement data of a user; and process the user movement data to determinea user gesture type and output gesture data; a mapping module to:receive the gesture data from the input capturing module; and map thegesture data into an input event on the computing device; generatemapped input data simulating the input event; and wherein the receiversharing module is to transmit the mapped input data to the computingdevice.
 23. The capturing system of claim 22, wherein to map the gesturedata into an input event on the computing device, the mapping module isto: retrieve a type of movement of the user from the gesture data; anddetermine the input event based on the type of movement.
 24. Thecapturing system of claim 23, wherein when the type of movement of theuser is a swipe movement the gesture data is mapped to a touch inputevent and wherein the mapped input data includes data simulating thetouch input event for a touch sensor of the computing device.
 25. Thecapturing system of claim 23, wherein when the type of movement of theuser is a lean movement the gesture data is mapped to a rotate inputevent and wherein the mapped input include data simulating the rotateinput event is provided for a gyroscope of the computing device.